Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f506a8b8d3af253f677598c8b6b3dda7c05dd5031418b041d1b8dd3d2646ae90

Tx prefix hash: ddb4e40e0660bb08ae53241a81deb0520fef13ad0fca7467cd468b35f7130f2b
Tx public key: 36b9ffff5edd3024d04ed9727f3e8e5cec2f146c69381e0a508adb6e5f1d3bde
Timestamp: 1577524072 Timestamp [UCT]: 2019-12-28 09:07:52 Age [y:d:h:m:s]: 05:308:20:54:08
Block: 33313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1368424 RingCT/type: yes/0
Extra: 0136b9ffff5edd3024d04ed9727f3e8e5cec2f146c69381e0a508adb6e5f1d3bde021100000003d81c26c0000000000000000000

1 output(s) for total of 476.015461763000 dcy

stealth address amount amount idx
00: 1ddcf869cc5f9164bc46f9cf8eba619375521c742aaf8b1561d1072c658ee1c6 476.015461763000 55758 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": 33323, "vin": [ { "gen": { "height": 33313 } } ], "vout": [ { "amount": 476015461763, "target": { "key": "1ddcf869cc5f9164bc46f9cf8eba619375521c742aaf8b1561d1072c658ee1c6" } } ], "extra": [ 1, 54, 185, 255, 255, 94, 221, 48, 36, 208, 78, 217, 114, 127, 62, 142, 92, 236, 47, 20, 108, 105, 56, 30, 10, 80, 138, 219, 110, 95, 29, 59, 222, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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