Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc3c8b97e41ec907b1bba653735caff7ed5c30074fa43104004f6826c09f0584

Tx prefix hash: 3f749c3c6ece5548ce04fdb28ef9c21f4eeb12ae2883f94c6091bd027640c512
Tx public key: 31dc4a4e86bc99f1b665078d3588301fbfa99f5de7a8dba3dc9127715f6b512e
Timestamp: 1715606664 Timestamp [UCT]: 2024-05-13 13:24:24 Age [y:d:h:m:s]: 00:340:02:00:57
Block: 1021151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243081 RingCT/type: yes/0
Extra: 0131dc4a4e86bc99f1b665078d3588301fbfa99f5de7a8dba3dc9127715f6b512e02110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f80e891c761485a7cebb038f3f01be696f066645a7ca604a03887c10f930ef90 0.600000000000 1485378 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": 1021161, "vin": [ { "gen": { "height": 1021151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f80e891c761485a7cebb038f3f01be696f066645a7ca604a03887c10f930ef90" } } ], "extra": [ 1, 49, 220, 74, 78, 134, 188, 153, 241, 182, 101, 7, 141, 53, 136, 48, 31, 191, 169, 159, 93, 231, 168, 219, 163, 220, 145, 39, 113, 95, 107, 81, 46, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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