Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29f2c96e60bfbf30ec87efd4d59cbf32f7ad2f63475dbddc647d17d5917b304f

Tx prefix hash: 9fe778d2689c7a6f0b4219397df43e4cbd72cd6f8e8f2faa772fc15f27aeac79
Tx public key: 3c5d08481076b994d0ecbcd850174d5fe92f6f1fdb4ec5452fea6ef245137002
Timestamp: 1723985317 Timestamp [UCT]: 2024-08-18 12:48:37 Age [y:d:h:m:s]: 00:240:05:44:31
Block: 1090601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171569 RingCT/type: yes/0
Extra: 013c5d08481076b994d0ecbcd850174d5fe92f6f1fdb4ec5452fea6ef24513700202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ea06405e049613eb3a5cf5b281b95a4dd6fd540dc563d408522b5d205f37c81 0.600000000000 1565224 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": 1090611, "vin": [ { "gen": { "height": 1090601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ea06405e049613eb3a5cf5b281b95a4dd6fd540dc563d408522b5d205f37c81" } } ], "extra": [ 1, 60, 93, 8, 72, 16, 118, 185, 148, 208, 236, 188, 216, 80, 23, 77, 95, 233, 47, 111, 31, 219, 78, 197, 69, 47, 234, 110, 242, 69, 19, 112, 2, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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