Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e72f77fd7bc7bad55ac32aaf9ff4f5a8a9c39a88c04f90c8e0c39d76b8274151

Tx prefix hash: 407a8d4c7dae6dc0e05c195d5cb9943e0c932488b09da633bca7031802c16c79
Tx public key: 26392baa4652003d48d5a84a645f5620c1e8cf836d980addd1a5e51a9dd5f087
Timestamp: 1764973571 Timestamp [UCT]: 2025-12-05 22:26:11 Age [y:d:h:m:s]: 00:001:00:42:58
Block: 1427271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 744 RingCT/type: yes/0
Extra: 0126392baa4652003d48d5a84a645f5620c1e8cf836d980addd1a5e51a9dd5f087021100000008d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69304a394bd3f63838192cc49d346ea9f7ebc151122af8bc371e6b1ef96b8f28 0.600000000000 1915972 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": 1427281, "vin": [ { "gen": { "height": 1427271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69304a394bd3f63838192cc49d346ea9f7ebc151122af8bc371e6b1ef96b8f28" } } ], "extra": [ 1, 38, 57, 43, 170, 70, 82, 0, 61, 72, 213, 168, 74, 100, 95, 86, 32, 193, 232, 207, 131, 109, 152, 10, 221, 209, 165, 229, 26, 157, 213, 240, 135, 2, 17, 0, 0, 0, 8, 214, 225, 157, 124, 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