Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a17b5c00c6d1220fa8e70fb1452df298f12cde5c8f2808f8601366488e809906

Tx prefix hash: fabc1398478de45133e03d8cfa9b6dc63b414024210fec440dd18ebd63f05950
Tx public key: 0ee1cde8d00dc73fbb6738fd80f5c0d7ef85522cc50f8e7b6a94c646aa05e583
Timestamp: 1689460355 Timestamp [UCT]: 2023-07-15 22:32:35 Age [y:d:h:m:s]: 01:226:08:38:20
Block: 804639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422848 RingCT/type: yes/0
Extra: 010ee1cde8d00dc73fbb6738fd80f5c0d7ef85522cc50f8e7b6a94c646aa05e583021100000002faf35c9c000000000000000000

1 output(s) for total of 1.324027772000 dcy

stealth address amount amount idx
00: 0f2fb1f2323f1479f507b9a18fd3cd7d5dd1744ec81e2a31dd0cedf34f9f3e6f 1.324027772000 1255844 of 0

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": 804649, "vin": [ { "gen": { "height": 804639 } } ], "vout": [ { "amount": 1324027772, "target": { "key": "0f2fb1f2323f1479f507b9a18fd3cd7d5dd1744ec81e2a31dd0cedf34f9f3e6f" } } ], "extra": [ 1, 14, 225, 205, 232, 208, 13, 199, 63, 187, 103, 56, 253, 128, 245, 192, 215, 239, 133, 82, 44, 197, 15, 142, 123, 106, 148, 198, 70, 170, 5, 229, 131, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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