Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27e7a62476683447018691e239d74b560185f1625f0e63ab918d89f6328b4c0c

Tx prefix hash: 3ef41fee35150a6d376a9ca9f8d00161af7fdb2b9cd21caa7e79c194dd931e49
Tx public key: 9473a6dfe0bde918bbb5e98af71c7c6ac88eb1ff1ebc29fc313dbff7b678d547
Timestamp: 1701284106 Timestamp [UCT]: 2023-11-29 18:55:06 Age [y:d:h:m:s]: 01:114:04:07:32
Block: 902379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342772 RingCT/type: yes/0
Extra: 019473a6dfe0bde918bbb5e98af71c7c6ac88eb1ff1ebc29fc313dbff7b678d547021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.628121642000 dcy

stealth address amount amount idx
00: e1ab188bf56dfbaca42ca9d99a30897fd0992dde8012a23c15611920add98460 0.628121642000 1359018 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": 902389, "vin": [ { "gen": { "height": 902379 } } ], "vout": [ { "amount": 628121642, "target": { "key": "e1ab188bf56dfbaca42ca9d99a30897fd0992dde8012a23c15611920add98460" } } ], "extra": [ 1, 148, 115, 166, 223, 224, 189, 233, 24, 187, 181, 233, 138, 247, 28, 124, 106, 200, 142, 177, 255, 30, 188, 41, 252, 49, 61, 191, 247, 182, 120, 213, 71, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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