Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab605c60671d781812f56697d1d52d8aa068430e9e71e0dd787d2562ffc04086

Tx prefix hash: 124e6e307c0bf69b9e7e47dcafbab558e4493c91a678f5d07e1f29d581d2ea92
Tx public key: 07e112d9cf847dc9ffe2c56f3ff0dc897ae4f063a3b4b70f6c41cfa1ae024f63
Timestamp: 1576430938 Timestamp [UCT]: 2019-12-15 17:28:58 Age [y:d:h:m:s]: 05:090:03:11:43
Block: 27843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1210802 RingCT/type: yes/0
Extra: 0107e112d9cf847dc9ffe2c56f3ff0dc897ae4f063a3b4b70f6c41cfa1ae024f630211000000044943cd9f000000000000000000

1 output(s) for total of 496.477630553000 dcy

stealth address amount amount idx
00: e7277ded570491631d58fedbd1f27be28813846c2a0ed53e99a9609b4147bc48 496.477630553000 45931 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": 27853, "vin": [ { "gen": { "height": 27843 } } ], "vout": [ { "amount": 496477630553, "target": { "key": "e7277ded570491631d58fedbd1f27be28813846c2a0ed53e99a9609b4147bc48" } } ], "extra": [ 1, 7, 225, 18, 217, 207, 132, 125, 201, 255, 226, 197, 111, 63, 240, 220, 137, 122, 228, 240, 99, 163, 180, 183, 15, 108, 65, 207, 161, 174, 2, 79, 99, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 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