Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 6c8f51495a2162d673dd1e15827f9b01f0329e15baabfc938ba3c221daf43e32

Tx prefix hash: 3e136c8cd475d09c43a9ffad5ddfcfa93ba4eadf449539b7e8243bb0bb015374
Tx public key: fd0134ccdf34964d0bd9cc7e71021e96629fa8db4da7b33a913a36de7a80d068
Timestamp: 1704629747 Timestamp [UCT]: 2024-01-07 12:15:47 Age [y:d:h:m:s]: 01:315:16:46:41
Block: 930107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484481 RingCT/type: yes/0
Extra: 01fd0134ccdf34964d0bd9cc7e71021e96629fa8db4da7b33a913a36de7a80d0680211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cf27cfa057219fc31c380c876e10f04191e60d4c98a3ed91a6428d69c83eefd 0.600000000000 1387985 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 930117, "vin": [ { "gen": { "height": 930107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cf27cfa057219fc31c380c876e10f04191e60d4c98a3ed91a6428d69c83eefd" } } ], "extra": [ 1, 253, 1, 52, 204, 223, 52, 150, 77, 11, 217, 204, 126, 113, 2, 30, 150, 98, 159, 168, 219, 77, 167, 179, 58, 145, 58, 54, 222, 122, 128, 208, 104, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8