Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1f37f8478759e7b4e9fc294959d509721d5f28779d979aa4e379218c48b67dd

Tx prefix hash: 6c9be1125fe25e6a4fab511abeb2ed97567a3fe0af37202bdc579e1679c830e0
Tx public key: 2f0206eb3f59b279cd8dba5aef7e687c4b52905d2e10ab584b17b1a2f1d88496
Timestamp: 1703705825 Timestamp [UCT]: 2023-12-27 19:37:05 Age [y:d:h:m:s]: 01:101:16:10:58
Block: 922468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333775 RingCT/type: yes/0
Extra: 012f0206eb3f59b279cd8dba5aef7e687c4b52905d2e10ab584b17b1a2f1d8849602110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f509266759a2e257b81a85530853e73c0a15589839c529e81cb99594a45de26 0.600000000000 1380166 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": 922478, "vin": [ { "gen": { "height": 922468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f509266759a2e257b81a85530853e73c0a15589839c529e81cb99594a45de26" } } ], "extra": [ 1, 47, 2, 6, 235, 63, 89, 178, 121, 205, 141, 186, 90, 239, 126, 104, 124, 75, 82, 144, 93, 46, 16, 171, 88, 75, 23, 177, 162, 241, 216, 132, 150, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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