Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef33d62f1562520204e0d88ed2878066c7f24ab636ba6aad37e8eacebbbac507

Tx prefix hash: 537f86818288befe1cde8570ca2eb19c71b2a9b93f22b1e97a8bc6c16eb875a8
Tx public key: 03e3cd97f624dfda8a93dcd0059e8c720dda1098bb59d0a72e5cfe67c916d0ce
Timestamp: 1723182641 Timestamp [UCT]: 2024-08-09 05:50:41 Age [y:d:h:m:s]: 00:313:04:53:01
Block: 1083941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223658 RingCT/type: yes/0
Extra: 0103e3cd97f624dfda8a93dcd0059e8c720dda1098bb59d0a72e5cfe67c916d0ce02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 748fa00993811e76a8b8c885ae4df1ff3be7ddc485d5cc51f3b28aa54a560e2b 0.600000000000 1558036 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": 1083951, "vin": [ { "gen": { "height": 1083941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "748fa00993811e76a8b8c885ae4df1ff3be7ddc485d5cc51f3b28aa54a560e2b" } } ], "extra": [ 1, 3, 227, 205, 151, 246, 36, 223, 218, 138, 147, 220, 208, 5, 158, 140, 114, 13, 218, 16, 152, 187, 89, 208, 167, 46, 92, 254, 103, 201, 22, 208, 206, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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