Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66689e5607ef3add700002202c845f0972651156ba50b4dc757af9e3938a688f

Tx prefix hash: d3c09f2f0ece0dfc2be04e77b45f11b8c3efb33fea49d9e45f9a41b107027435
Tx public key: 655ad70374df79e5a862145e8655b459a49c1e2044a2a87322fa0d2c2b8e4198
Timestamp: 1636938329 Timestamp [UCT]: 2021-11-15 01:05:29 Age [y:d:h:m:s]: 03:055:02:46:40
Block: 374483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 818141 RingCT/type: yes/0
Extra: 01655ad70374df79e5a862145e8655b459a49c1e2044a2a87322fa0d2c2b8e4198021100000005e59f5d07000000000000000000

1 output(s) for total of 35.251918179000 dcy

stealth address amount amount idx
00: ef55beb7c59834144ef17e8c7602a1ee68212302365e46cff44fb1efcd49081f 35.251918179000 757987 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": 374493, "vin": [ { "gen": { "height": 374483 } } ], "vout": [ { "amount": 35251918179, "target": { "key": "ef55beb7c59834144ef17e8c7602a1ee68212302365e46cff44fb1efcd49081f" } } ], "extra": [ 1, 101, 90, 215, 3, 116, 223, 121, 229, 168, 98, 20, 94, 134, 85, 180, 89, 164, 156, 30, 32, 68, 162, 168, 115, 34, 250, 13, 44, 43, 142, 65, 152, 2, 17, 0, 0, 0, 5, 229, 159, 93, 7, 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