Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76ce474addfb5395f778a38f569c43c212b1500bbd9d3d4e89734e2de791b734

Tx prefix hash: bf1577d1d98161f68dce5bcfacac3a0c8582330317d8c0d0a419d04d4e0347dc
Tx public key: 15430df6c2e327674bf40f08cd1b5ee92ffff9f64768c85138c2a137422fd18a
Timestamp: 1738286917 Timestamp [UCT]: 2025-01-31 01:28:37 Age [y:d:h:m:s]: 00:136:11:28:32
Block: 1208740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97511 RingCT/type: yes/0
Extra: 0115430df6c2e327674bf40f08cd1b5ee92ffff9f64768c85138c2a137422fd18a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e51318fc1d4ecbced184261c2f8ed76431ce11bec8fdb354e40b1beaeafcb961 0.600000000000 1695475 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": 1208750, "vin": [ { "gen": { "height": 1208740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e51318fc1d4ecbced184261c2f8ed76431ce11bec8fdb354e40b1beaeafcb961" } } ], "extra": [ 1, 21, 67, 13, 246, 194, 227, 39, 103, 75, 244, 15, 8, 205, 27, 94, 233, 47, 255, 249, 246, 71, 104, 200, 81, 56, 194, 161, 55, 66, 47, 209, 138, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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