Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0614527376fa0eabdccd1a4bd6255c0ea52cad3bd1cfde9f6aa104e987d4644a

Tx prefix hash: fb5c82242fa17e3fd9e4ad3751cec44913ba1b265b053e1c143bfeda200b3d66
Tx public key: 96e73997a9461d0606e84f7112d8a1df979ae65932b96880569dea0de49f5f91
Timestamp: 1711447279 Timestamp [UCT]: 2024-03-26 10:01:19 Age [y:d:h:m:s]: 01:012:05:10:21
Block: 986671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269679 RingCT/type: yes/0
Extra: 0196e73997a9461d0606e84f7112d8a1df979ae65932b96880569dea0de49f5f910211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1a241f1b2d6632e3777b20b06c3dd90dc9c25de07027064f027c737d0ceb0f5 0.600000000000 1446904 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": 986681, "vin": [ { "gen": { "height": 986671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1a241f1b2d6632e3777b20b06c3dd90dc9c25de07027064f027c737d0ceb0f5" } } ], "extra": [ 1, 150, 231, 57, 151, 169, 70, 29, 6, 6, 232, 79, 113, 18, 216, 161, 223, 151, 154, 230, 89, 50, 185, 104, 128, 86, 157, 234, 13, 228, 159, 95, 145, 2, 17, 0, 0, 0, 4, 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