Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 574a8097565330ad0c7145460fd58f8616261d14fb3dfedc6119c5a2590c0e26

Tx prefix hash: ea71ad72d737a2ec219d2dd55554e51b4e1f6f749e11a67a078ee52b4729d5c2
Tx public key: 48d5e46a54a03057d3d2eeee9b75a2ed817fe4477a13f8fb363f6fc31e4a8427
Timestamp: 1727654001 Timestamp [UCT]: 2024-09-29 23:53:21 Age [y:d:h:m:s]: 00:055:15:39:02
Block: 1121011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39778 RingCT/type: yes/0
Extra: 0148d5e46a54a03057d3d2eeee9b75a2ed817fe4477a13f8fb363f6fc31e4a842702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aeab4c3fa3d60ed9655a42c573201fe8a5c270691b79144ed5c800661a74c8ea 0.600000000000 1603130 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": 1121021, "vin": [ { "gen": { "height": 1121011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aeab4c3fa3d60ed9655a42c573201fe8a5c270691b79144ed5c800661a74c8ea" } } ], "extra": [ 1, 72, 213, 228, 106, 84, 160, 48, 87, 211, 210, 238, 238, 155, 117, 162, 237, 129, 127, 228, 71, 122, 19, 248, 251, 54, 63, 111, 195, 30, 74, 132, 39, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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