Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da7cb64c961369ac3bd0af8ebc418bea2f246a1652e3fc347812cb16d8131437

Tx prefix hash: 4a09680f05858689400d1f0c87fcd4df36b9d90ee74ae2bdd9e5cbc79ecbb8c9
Tx public key: f484c6ecfa9ea29c7aae7524d8ca00dc99c1fe33dd9d941c3e77d910bd36f5a1
Timestamp: 1723759650 Timestamp [UCT]: 2024-08-15 22:07:30 Age [y:d:h:m:s]: 00:230:16:16:38
Block: 1088725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164736 RingCT/type: yes/0
Extra: 01f484c6ecfa9ea29c7aae7524d8ca00dc99c1fe33dd9d941c3e77d910bd36f5a1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a3816fa3e133e6f2ab3288371a3c5aa909a00e5ff940da8d2c0c80e4a61287d 0.600000000000 1563342 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": 1088735, "vin": [ { "gen": { "height": 1088725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a3816fa3e133e6f2ab3288371a3c5aa909a00e5ff940da8d2c0c80e4a61287d" } } ], "extra": [ 1, 244, 132, 198, 236, 250, 158, 162, 156, 122, 174, 117, 36, 216, 202, 0, 220, 153, 193, 254, 51, 221, 157, 148, 28, 62, 119, 217, 16, 189, 54, 245, 161, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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