Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 213a67d9b5d9a0d6b74b643734cd79f514f3d431dda4a3beaec6b63c2502da08

Tx prefix hash: a1cdfc5ec1d1a614ec4868362fa1dc33844bdf1eccfec52f80a54504a92f9ecb
Tx public key: 39236b9fc32e6d0b455350c5f17b6cbd731d4c80db8f72dcc5e7631bb37a87c9
Timestamp: 1687785818 Timestamp [UCT]: 2023-06-26 13:23:38 Age [y:d:h:m:s]: 01:289:22:32:28
Block: 790747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468381 RingCT/type: yes/0
Extra: 0139236b9fc32e6d0b455350c5f17b6cbd731d4c80db8f72dcc5e7631bb37a87c90211000000024b8f5122000000000000000000

1 output(s) for total of 1.472065308000 dcy

stealth address amount amount idx
00: d7d968be33f04c12f06c262dc0f12842e7d3c565dde5b900f7df6529fc3f8ad2 1.472065308000 1241160 of 0

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": 790757, "vin": [ { "gen": { "height": 790747 } } ], "vout": [ { "amount": 1472065308, "target": { "key": "d7d968be33f04c12f06c262dc0f12842e7d3c565dde5b900f7df6529fc3f8ad2" } } ], "extra": [ 1, 57, 35, 107, 159, 195, 46, 109, 11, 69, 83, 80, 197, 241, 123, 108, 189, 115, 29, 76, 128, 219, 143, 114, 220, 197, 231, 99, 27, 179, 122, 135, 201, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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