Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa9847861888f410c4c927f0db9110d10177cca3d786dd6df8df72e78af30f5a

Tx prefix hash: 145546bbdcb7c2a54f1442165def254a04df2c8d6c66161c1ab1e33f05caaf7e
Tx public key: 695380bd9b4de213c5559d0b1bb43dd19563f1d9deb5aeaa7bd139b980e88ac4
Timestamp: 1575051204 Timestamp [UCT]: 2019-11-29 18:13:24 Age [y:d:h:m:s]: 05:131:19:34:00
Block: 19903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1237115 RingCT/type: yes/0
Extra: 01695380bd9b4de213c5559d0b1bb43dd19563f1d9deb5aeaa7bd139b980e88ac4021100000033ad433a0b000000000000000000

1 output(s) for total of 527.295391717000 dcy

stealth address amount amount idx
00: 54420162b5ff6379383d41d42f8639146203f460f69f50822809b657957a05e4 527.295391717000 31725 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": 19913, "vin": [ { "gen": { "height": 19903 } } ], "vout": [ { "amount": 527295391717, "target": { "key": "54420162b5ff6379383d41d42f8639146203f460f69f50822809b657957a05e4" } } ], "extra": [ 1, 105, 83, 128, 189, 155, 77, 226, 19, 197, 85, 157, 11, 27, 180, 61, 209, 149, 99, 241, 217, 222, 181, 174, 170, 123, 209, 57, 185, 128, 232, 138, 196, 2, 17, 0, 0, 0, 51, 173, 67, 58, 11, 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