Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af6d9caa9ba2696d0f434fc153ea4f2778e78ed2ec319b3658405ce49bbb990d

Tx prefix hash: b8713c0eb84ade2bded4de3a5d722ce8261181ea92cbbec8c4e5e19dfea3d499
Tx public key: 8d44f8d61c78db81e9458daf491b9b7d60fd60d7c59ddc2ca636bab92c16c1dd
Timestamp: 1725159267 Timestamp [UCT]: 2024-09-01 02:54:27 Age [y:d:h:m:s]: 01:060:03:00:37
Block: 1100324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301412 RingCT/type: yes/0
Extra: 018d44f8d61c78db81e9458daf491b9b7d60fd60d7c59ddc2ca636bab92c16c1dd021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5490d8477f49905236dbe2a3e9118a767274a70ca296e7e371a702adb13867a 0.600000000000 1576299 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": 1100334, "vin": [ { "gen": { "height": 1100324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5490d8477f49905236dbe2a3e9118a767274a70ca296e7e371a702adb13867a" } } ], "extra": [ 1, 141, 68, 248, 214, 28, 120, 219, 129, 233, 69, 141, 175, 73, 27, 155, 125, 96, 253, 96, 215, 197, 157, 220, 44, 166, 54, 186, 185, 44, 22, 193, 221, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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