Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf0fff2f455856e6e3330779f78cd53fb224d512085b85caf5791d7be6a4b4b0

Tx prefix hash: 78c0be368c6c4be51a3cdf3bc1551aa7e314eeb85d59c496a857a434fe97a06c
Tx public key: 7ae7e9aa927fdf052117ab44517bcc2a04816ec174f4d28801f2ab2c4d373ff6
Timestamp: 1750963599 Timestamp [UCT]: 2025-06-26 18:46:39 Age [y:d:h:m:s]: 00:147:12:39:27
Block: 1313350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103441 RingCT/type: yes/0
Extra: 017ae7e9aa927fdf052117ab44517bcc2a04816ec174f4d28801f2ab2c4d373ff6021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d351c567c796a97757f2e0fcb88bbb00383f5c3acab3e6764786ae7098d7176 0.600000000000 1800989 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": 1313360, "vin": [ { "gen": { "height": 1313350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d351c567c796a97757f2e0fcb88bbb00383f5c3acab3e6764786ae7098d7176" } } ], "extra": [ 1, 122, 231, 233, 170, 146, 127, 223, 5, 33, 23, 171, 68, 81, 123, 204, 42, 4, 129, 110, 193, 116, 244, 210, 136, 1, 242, 171, 44, 77, 55, 63, 246, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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