Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0defdaa354ad70e8bde90b4359228e714ef55d1fc3a85847e96692eb6d35ec5

Tx prefix hash: c2c18f28d9d1c3302446b93ca2e87d7cda8760cb03b69bd197bc9859972b81cd
Tx public key: bf8db80b5dad9b33313a307474b2b7a8f235bda0564bb7c413ae59adedfec2f5
Timestamp: 1727950166 Timestamp [UCT]: 2024-10-03 10:09:26 Age [y:d:h:m:s]: 00:110:14:56:51
Block: 1123469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79044 RingCT/type: yes/0
Extra: 01bf8db80b5dad9b33313a307474b2b7a8f235bda0564bb7c413ae59adedfec2f5021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51ac6936a1406f03c9187b9899bb93adf267e84e9f3d8d714a25765485046a9f 0.600000000000 1606004 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": 1123479, "vin": [ { "gen": { "height": 1123469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51ac6936a1406f03c9187b9899bb93adf267e84e9f3d8d714a25765485046a9f" } } ], "extra": [ 1, 191, 141, 184, 11, 93, 173, 155, 51, 49, 58, 48, 116, 116, 178, 183, 168, 242, 53, 189, 160, 86, 75, 183, 196, 19, 174, 89, 173, 237, 254, 194, 245, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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