Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 249b292cab8aab94b651f4d5782c5f0da2cbd92a7a0161bbcaae643e7e339ba9

Tx prefix hash: d99bcf3fd2a21c2fc3c553f8ee0dd758ec74651d9a25c6f15b657f4afe481f72
Tx public key: f91726e7f204196b4ac3ed53071621f07fd4caaeaf6ba752345ac070880e4aaa
Timestamp: 1761013993 Timestamp [UCT]: 2025-10-21 02:33:13 Age [y:d:h:m:s]: 00:067:19:45:05
Block: 1394481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48549 RingCT/type: yes/0
Extra: 01f91726e7f204196b4ac3ed53071621f07fd4caaeaf6ba752345ac070880e4aaa0211000000098368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a75a1a4f3ed1e33a64d8ec47d9cc2f0a4c7b277f365a294351897c8b54861334 0.600000000000 1882752 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": 1394491, "vin": [ { "gen": { "height": 1394481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a75a1a4f3ed1e33a64d8ec47d9cc2f0a4c7b277f365a294351897c8b54861334" } } ], "extra": [ 1, 249, 23, 38, 231, 242, 4, 25, 107, 74, 195, 237, 83, 7, 22, 33, 240, 127, 212, 202, 174, 175, 107, 167, 82, 52, 90, 192, 112, 136, 14, 74, 170, 2, 17, 0, 0, 0, 9, 131, 104, 38, 109, 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