Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8526657a3dd7a74f6cc2272540b1086055ccdfb1c4520dfebf0dac7740efd0e

Tx prefix hash: 34e1d4b9de0eaccac5e05425e4ad9e1d602fd76f08ed06f526a1a4177927f804
Tx public key: 0a3249911b056ce6e739f5d10a87e1cc9c07ca2c23b03cbfb333236ec7f74f05
Timestamp: 1634674784 Timestamp [UCT]: 2021-10-19 20:19:44 Age [y:d:h:m:s]: 03:111:02:12:27
Block: 356383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 857280 RingCT/type: yes/0
Extra: 010a3249911b056ce6e739f5d10a87e1cc9c07ca2c23b03cbfb333236ec7f74f050211000000118d0de867000000000000000000

1 output(s) for total of 40.472086408000 dcy

stealth address amount amount idx
00: 8315224bbe2c28bdf214dfb025d4ec687f09d4d315d584dd3911f7a39acdf42b 40.472086408000 727165 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": 356393, "vin": [ { "gen": { "height": 356383 } } ], "vout": [ { "amount": 40472086408, "target": { "key": "8315224bbe2c28bdf214dfb025d4ec687f09d4d315d584dd3911f7a39acdf42b" } } ], "extra": [ 1, 10, 50, 73, 145, 27, 5, 108, 230, 231, 57, 245, 209, 10, 135, 225, 204, 156, 7, 202, 44, 35, 176, 60, 191, 179, 51, 35, 110, 199, 247, 79, 5, 2, 17, 0, 0, 0, 17, 141, 13, 232, 103, 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