Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4508baefddf8de75f4954bbaad7810460393b6ff9217ee4f64d214996513346e

Tx prefix hash: 625029e16c0e4a40189cd41703b873abd8a99907072ba1c488db84c3ff06ac27
Tx public key: ef504df8ed2a992e2c7475ab5a676d2443a4d5d476dcff5c5b08d3715c9d8f1a
Timestamp: 1745782741 Timestamp [UCT]: 2025-04-27 19:39:01 Age [y:d:h:m:s]: 00:207:02:48:19
Block: 1270793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145737 RingCT/type: yes/0
Extra: 01ef504df8ed2a992e2c7475ab5a676d2443a4d5d476dcff5c5b08d3715c9d8f1a02110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fed5c8c6a2d528f365282512a0799f89d8e187b9e9a43037ed9bb8d9094747b 0.600000000000 1758038 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": 1270803, "vin": [ { "gen": { "height": 1270793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fed5c8c6a2d528f365282512a0799f89d8e187b9e9a43037ed9bb8d9094747b" } } ], "extra": [ 1, 239, 80, 77, 248, 237, 42, 153, 46, 44, 116, 117, 171, 90, 103, 109, 36, 67, 164, 213, 212, 118, 220, 255, 92, 91, 8, 211, 113, 92, 157, 143, 26, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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