Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 268b3b64a5d1775362ecba1f1c21b4b71a30bb5308389442d80b4fc48ac81f03

Tx prefix hash: 9fc7a53e81b1477cd659f72df93e18a4a0c6faf120b277fb88bbab8aa2af50b4
Tx public key: 0cf888168f61645acedd35b161e7e4f747cec650c5e97d0d915e9cd8ec148cfd
Timestamp: 1717713598 Timestamp [UCT]: 2024-06-06 22:39:58 Age [y:d:h:m:s]: 00:303:11:50:57
Block: 1038604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216894 RingCT/type: yes/0
Extra: 010cf888168f61645acedd35b161e7e4f747cec650c5e97d0d915e9cd8ec148cfd02110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae169e9d3ae3e69529194d14f9b6afd5aa0fb333cba7fff84616249e41100297 0.600000000000 1507165 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": 1038614, "vin": [ { "gen": { "height": 1038604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae169e9d3ae3e69529194d14f9b6afd5aa0fb333cba7fff84616249e41100297" } } ], "extra": [ 1, 12, 248, 136, 22, 143, 97, 100, 90, 206, 221, 53, 177, 97, 231, 228, 247, 71, 206, 198, 80, 197, 233, 125, 13, 145, 94, 156, 216, 236, 20, 140, 253, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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