Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4f952399caa7a50bf6a5d8ffb96fa2f2eb30ce0e1f9c61cd572d622fcf04e16

Tx prefix hash: 697c7c3449fae7a42c40ecb8452b8d5b73d4fd6796491901ccf28e5fa8c0b55a
Tx public key: 7172c0d9fea5db31adc1720dfb6ae3d4ca6bff1267f97fc67e6cae768d798a0d
Timestamp: 1750460442 Timestamp [UCT]: 2025-06-20 23:00:42 Age [y:d:h:m:s]: 00:153:01:34:33
Block: 1309349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107236 RingCT/type: yes/0
Extra: 017172c0d9fea5db31adc1720dfb6ae3d4ca6bff1267f97fc67e6cae768d798a0d02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7bd991249967641f3b18ae2477ea8a825c800e9c5969c3694c04a12ae671b4f 0.600000000000 1796964 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": 1309359, "vin": [ { "gen": { "height": 1309349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7bd991249967641f3b18ae2477ea8a825c800e9c5969c3694c04a12ae671b4f" } } ], "extra": [ 1, 113, 114, 192, 217, 254, 165, 219, 49, 173, 193, 114, 13, 251, 106, 227, 212, 202, 107, 255, 18, 103, 249, 127, 198, 126, 108, 174, 118, 141, 121, 138, 13, 2, 17, 0, 0, 0, 2, 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