Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a01126cff9130b005562a6ffaf21458c97ea8dc1677368597b5bd1cccb83c113

Tx prefix hash: bd159d27d4841c272543ead89718c6f7b157c8a791ea929d8522b0ac1f6cdb8c
Tx public key: 9f9d951da6e1235f62057bc87018e3700a8ead4b347023f06c0a342f888a2265
Timestamp: 1721572642 Timestamp [UCT]: 2024-07-21 14:37:22 Age [y:d:h:m:s]: 01:113:11:48:26
Block: 1070587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339625 RingCT/type: yes/0
Extra: 019f9d951da6e1235f62057bc87018e3700a8ead4b347023f06c0a342f888a22650211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69e5d33432a08bdd3208fb83676b6a48f815f7572b01d6bd140bf73bfeebdfeb 0.600000000000 1542482 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": 1070597, "vin": [ { "gen": { "height": 1070587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69e5d33432a08bdd3208fb83676b6a48f815f7572b01d6bd140bf73bfeebdfeb" } } ], "extra": [ 1, 159, 157, 149, 29, 166, 225, 35, 95, 98, 5, 123, 200, 112, 24, 227, 112, 10, 142, 173, 75, 52, 112, 35, 240, 108, 10, 52, 47, 136, 138, 34, 101, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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