Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94d4279f6b3c0951348be7b71c3c73ae049e9f05567d2a2b4ab7ace2fd852832

Tx prefix hash: 7852d8e86d6aee010065e200c4ba6ead5d80551bdc39a2883f40af95825161f2
Tx public key: 5cf2e726aa25a1e4e88705d42c523d89626650ef9ebf1484aabf74c131915b3f
Timestamp: 1750821765 Timestamp [UCT]: 2025-06-25 03:22:45 Age [y:d:h:m:s]: 00:147:10:45:48
Block: 1312261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103309 RingCT/type: yes/0
Extra: 015cf2e726aa25a1e4e88705d42c523d89626650ef9ebf1484aabf74c131915b3f02110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7327230c251fdeb6958bbe104309633cbd098747a36f504308f1d09df009b6c 0.600000000000 1799892 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": 1312271, "vin": [ { "gen": { "height": 1312261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7327230c251fdeb6958bbe104309633cbd098747a36f504308f1d09df009b6c" } } ], "extra": [ 1, 92, 242, 231, 38, 170, 37, 161, 228, 232, 135, 5, 212, 44, 82, 61, 137, 98, 102, 80, 239, 158, 191, 20, 132, 170, 191, 116, 193, 49, 145, 91, 63, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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