Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 923d9f6c09d0946ea2bdfc411ce58f9bf9b9df9a34794d57b3cf49dde364de92

Tx prefix hash: ebb538ffac113954c915543844f19a409a60332fdd8a72b63584b1d0b23c9ee3
Tx public key: 64259c86f5eb300a1c5937ae3cacf17056f9ca89620efff822a2f2fd37c22767
Timestamp: 1741194834 Timestamp [UCT]: 2025-03-05 17:13:54 Age [y:d:h:m:s]: 00:261:03:04:43
Block: 1232808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184379 RingCT/type: yes/0
Extra: 0164259c86f5eb300a1c5937ae3cacf17056f9ca89620efff822a2f2fd37c2276702110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3669be05c33c6d0f3bde18bda3fa9498277b16bd56003db7f7a35aa498de5577 0.600000000000 1719723 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": 1232818, "vin": [ { "gen": { "height": 1232808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3669be05c33c6d0f3bde18bda3fa9498277b16bd56003db7f7a35aa498de5577" } } ], "extra": [ 1, 100, 37, 156, 134, 245, 235, 48, 10, 28, 89, 55, 174, 60, 172, 241, 112, 86, 249, 202, 137, 98, 14, 255, 248, 34, 162, 242, 253, 55, 194, 39, 103, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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