Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7913faef074b4dfe9156d5ead0ba83a9789ce7e4a849e493a60772f8f9d08f18

Tx prefix hash: 0472c23a16c4bb144abac6bd8f4fbf35bb6ff922314bfb0e576e32836d16812f
Tx public key: 9143f13b84dc388565c948730f35f363be22272a26c2e1b2ac7894b4e4f15bc4
Timestamp: 1751295447 Timestamp [UCT]: 2025-06-30 14:57:27 Age [y:d:h:m:s]: 00:136:22:43:24
Block: 1315914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96064 RingCT/type: yes/0
Extra: 019143f13b84dc388565c948730f35f363be22272a26c2e1b2ac7894b4e4f15bc402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 366f03c368a3ff62a1d6aef27ac58f55c1b42fdbd2e64cf024bde0ceca2aac39 0.600000000000 1803571 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": 1315924, "vin": [ { "gen": { "height": 1315914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "366f03c368a3ff62a1d6aef27ac58f55c1b42fdbd2e64cf024bde0ceca2aac39" } } ], "extra": [ 1, 145, 67, 241, 59, 132, 220, 56, 133, 101, 201, 72, 115, 15, 53, 243, 99, 190, 34, 39, 42, 38, 194, 225, 178, 172, 120, 148, 180, 228, 241, 91, 196, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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