Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0ce2ab341f952adc1c4359958957ad8acbbc3f35707d3f2fdbb570939771ae9

Tx prefix hash: fa76fbb4c2843062c979a195c2a0f11f4136d48c690ada23ff4612509828044c
Tx public key: 14dc1d4aa40bbf215e7e5f404a1b404b193796723bac2ff1c66590ce7040ac1b
Timestamp: 1716348582 Timestamp [UCT]: 2024-05-22 03:29:42 Age [y:d:h:m:s]: 01:169:20:48:49
Block: 1027289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379996 RingCT/type: yes/0
Extra: 0114dc1d4aa40bbf215e7e5f404a1b404b193796723bac2ff1c66590ce7040ac1b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b3d5a24607d8d6c6b2ee561ea400c0febc99e5c8a8bd65a031936b075586320 0.600000000000 1494828 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": 1027299, "vin": [ { "gen": { "height": 1027289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b3d5a24607d8d6c6b2ee561ea400c0febc99e5c8a8bd65a031936b075586320" } } ], "extra": [ 1, 20, 220, 29, 74, 164, 11, 191, 33, 94, 126, 95, 64, 74, 27, 64, 75, 25, 55, 150, 114, 59, 172, 47, 241, 198, 101, 144, 206, 112, 64, 172, 27, 2, 17, 0, 0, 0, 2, 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