Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d40469dd228ae1befa2ca9046cef9d7700b742ea1a5843324137aadfe14265e

Tx prefix hash: 8e9291899815d0f3d5f830f3edb922278983c6c2570bc8e5ada08f4d18e82fc6
Tx public key: bf9b73d95adb137d2340ca6b750e0e56e843bc047ad0d66c99cfe3fc243ed663
Timestamp: 1716270795 Timestamp [UCT]: 2024-05-21 05:53:15 Age [y:d:h:m:s]: 00:280:08:21:11
Block: 1026651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200337 RingCT/type: yes/0
Extra: 01bf9b73d95adb137d2340ca6b750e0e56e843bc047ad0d66c99cfe3fc243ed66302110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b50776f7b617debb1c5fb5ebb52c41a8f8ec30f36ef2916d855936b97ed08d7 0.600000000000 1493848 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": 1026661, "vin": [ { "gen": { "height": 1026651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b50776f7b617debb1c5fb5ebb52c41a8f8ec30f36ef2916d855936b97ed08d7" } } ], "extra": [ 1, 191, 155, 115, 217, 90, 219, 19, 125, 35, 64, 202, 107, 117, 14, 14, 86, 232, 67, 188, 4, 122, 208, 214, 108, 153, 207, 227, 252, 36, 62, 214, 99, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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