Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5aa0dfd948ca6741d040a23dc434c49f412f1363603d941023bb4a2175024678

Tx prefix hash: 8caf0a48e8574ed073ada79f7721cc64caab339490dd977d229933eb2d13fc16
Tx public key: 16541750306fb4de8d8ef054bb6d2b1bc5f7103429e34afb92ee9f3189e787ec
Timestamp: 1637765124 Timestamp [UCT]: 2021-11-24 14:45:24 Age [y:d:h:m:s]: 03:110:19:12:51
Block: 381165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 857883 RingCT/type: yes/0
Extra: 0116541750306fb4de8d8ef054bb6d2b1bc5f7103429e34afb92ee9f3189e787ec0211000000044a0f5013000000000000000000

1 output(s) for total of 33.500402422000 dcy

stealth address amount amount idx
00: 0cfb42ac03973f74b27fb1924c89cebe59b98dd9b7f7bea4c826daf47c0bc86e 33.500402422000 770109 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": 381175, "vin": [ { "gen": { "height": 381165 } } ], "vout": [ { "amount": 33500402422, "target": { "key": "0cfb42ac03973f74b27fb1924c89cebe59b98dd9b7f7bea4c826daf47c0bc86e" } } ], "extra": [ 1, 22, 84, 23, 80, 48, 111, 180, 222, 141, 142, 240, 84, 187, 109, 43, 27, 197, 247, 16, 52, 41, 227, 74, 251, 146, 238, 159, 49, 137, 231, 135, 236, 2, 17, 0, 0, 0, 4, 74, 15, 80, 19, 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