Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15a8f0ea9b2ee3c97cf6628183328711acb97ca4eda973ec504eb28dff39a2b5

Tx prefix hash: 52c53661b1ffa7bcc16afdf6a6f48fc0b9f29a96f2889642762a5123fd00e97f
Tx public key: d8556aa91b65e55589a3ebc4c8ae8ddc8e74fd2b6d48d73de71eeac473a8fdd4
Timestamp: 1699126204 Timestamp [UCT]: 2023-11-04 19:30:04 Age [y:d:h:m:s]: 01:076:13:40:36
Block: 884756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315859 RingCT/type: yes/0
Extra: 01d8556aa91b65e55589a3ebc4c8ae8ddc8e74fd2b6d48d73de71eeac473a8fdd402110000000433af99f4000000000000000000

1 output(s) for total of 0.718515428000 dcy

stealth address amount amount idx
00: 8b5e9043d2676cef27b75388e1d0aef14eb21dc11893ec3e344a0aed4d4f20d7 0.718515428000 1340503 of 0

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": 884766, "vin": [ { "gen": { "height": 884756 } } ], "vout": [ { "amount": 718515428, "target": { "key": "8b5e9043d2676cef27b75388e1d0aef14eb21dc11893ec3e344a0aed4d4f20d7" } } ], "extra": [ 1, 216, 85, 106, 169, 27, 101, 229, 85, 137, 163, 235, 196, 200, 174, 141, 220, 142, 116, 253, 43, 109, 72, 215, 61, 231, 30, 234, 196, 115, 168, 253, 212, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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