Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0dca38218eed668cebab02b38a6bdc19c00e3ee8964b55ca30a3e0a9c726f36

Tx prefix hash: bd89747d8788216e68d342cefa76a75782d227824325cd07ab687f7c2db31310
Tx public key: 6298539ba74b7ff0b0f4d1de3c0b068ae7b1fc1da2d0a4fef929ef3edd9f33fd
Timestamp: 1672638836 Timestamp [UCT]: 2023-01-02 05:53:56 Age [y:d:h:m:s]: 02:017:05:03:19
Block: 665772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 534208 RingCT/type: yes/0
Extra: 016298539ba74b7ff0b0f4d1de3c0b068ae7b1fc1da2d0a4fef929ef3edd9f33fd02110000000552542ceb000000000000000000

1 output(s) for total of 3.819626980000 dcy

stealth address amount amount idx
00: f6912435613e8982e1ddf629186c43dd47ce795a1638450387e12de0615ef8e3 3.819626980000 1106831 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": 665782, "vin": [ { "gen": { "height": 665772 } } ], "vout": [ { "amount": 3819626980, "target": { "key": "f6912435613e8982e1ddf629186c43dd47ce795a1638450387e12de0615ef8e3" } } ], "extra": [ 1, 98, 152, 83, 155, 167, 75, 127, 240, 176, 244, 209, 222, 60, 11, 6, 138, 231, 177, 252, 29, 162, 208, 164, 254, 249, 41, 239, 62, 221, 159, 51, 253, 2, 17, 0, 0, 0, 5, 82, 84, 44, 235, 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