Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91b57ad9f5f9b6e5c3976b12550900a43a5af1acd7fb01e4423e0ea31c56504c

Tx prefix hash: b5a40fea1e1eb0927c38b8d0b9c958a6c5f18fec2091da746b2c158eb01467f5
Tx public key: 4d616a1996c556f87cee3ef630b9e8487d9caa5c35b79dd547c29467cc80d658
Timestamp: 1715454836 Timestamp [UCT]: 2024-05-11 19:13:56 Age [y:d:h:m:s]: 00:328:08:45:03
Block: 1019904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234676 RingCT/type: yes/0
Extra: 014d616a1996c556f87cee3ef630b9e8487d9caa5c35b79dd547c29467cc80d65802110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c062ed3941e87c4343f980d1f6dde5ffe6ddacf897b988dccdbba31d6a77664 0.600000000000 1483957 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": 1019914, "vin": [ { "gen": { "height": 1019904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c062ed3941e87c4343f980d1f6dde5ffe6ddacf897b988dccdbba31d6a77664" } } ], "extra": [ 1, 77, 97, 106, 25, 150, 197, 86, 248, 124, 238, 62, 246, 48, 185, 232, 72, 125, 156, 170, 92, 53, 183, 157, 213, 71, 194, 148, 103, 204, 128, 214, 88, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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