Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ba1f66da1598a751e9853a0b6bfdc2cefd99faf114cccd5fa4a24b3f2906997

Tx prefix hash: 1b4b04d849763e9910c1a250eb1fd300a42dab7ff927fd878c4033178e27c3f9
Tx public key: 248c852dbde956d2a85af5e13b2a9e705e736fb337d2c11354fd037eec69f391
Timestamp: 1704281190 Timestamp [UCT]: 2024-01-03 11:26:30 Age [y:d:h:m:s]: 01:015:20:31:46
Block: 927239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272659 RingCT/type: yes/0
Extra: 01248c852dbde956d2a85af5e13b2a9e705e736fb337d2c11354fd037eec69f3910211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a4399ecc494814fb5d8a068cc203c999b47970527dd257511084af18d0b87f6 0.600000000000 1385051 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": 927249, "vin": [ { "gen": { "height": 927239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a4399ecc494814fb5d8a068cc203c999b47970527dd257511084af18d0b87f6" } } ], "extra": [ 1, 36, 140, 133, 45, 189, 233, 86, 210, 168, 90, 245, 225, 59, 42, 158, 112, 94, 115, 111, 179, 55, 210, 193, 19, 84, 253, 3, 126, 236, 105, 243, 145, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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