Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d58cba132fc921f6c51a36a58a3714269cef61da4d765e1936aa3c9b8537393b

Tx prefix hash: 756299d6583ee80e348571bfd539baefdff2f6df5cc0deeff654d4dbdea88ce3
Tx public key: b2e98f8cfe5d0fe92982ed8cb7691a7531bcd7115dbfb50a6fe1dc76210d94bf
Timestamp: 1734509318 Timestamp [UCT]: 2024-12-18 08:08:38 Age [y:d:h:m:s]: 00:133:07:46:06
Block: 1177756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95064 RingCT/type: yes/0
Extra: 01b2e98f8cfe5d0fe92982ed8cb7691a7531bcd7115dbfb50a6fe1dc76210d94bf0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e13487f68fd37b067182b4b9d2c30bfead5a043580756aff1153d240e42ec2f5 0.600000000000 1664133 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": 1177766, "vin": [ { "gen": { "height": 1177756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e13487f68fd37b067182b4b9d2c30bfead5a043580756aff1153d240e42ec2f5" } } ], "extra": [ 1, 178, 233, 143, 140, 254, 93, 15, 233, 41, 130, 237, 140, 183, 105, 26, 117, 49, 188, 215, 17, 93, 191, 181, 10, 111, 225, 220, 118, 33, 13, 148, 191, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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