Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb7a276c9303d3b171302f4f150d3bca17b108a63a61db779f911d9b07a0b384

Tx prefix hash: 57a7eb6ef3e622922fdf59c09796d4505953c790a7b02151f7f60e549813590b
Tx public key: 5ef008a510af91cf8c775981fdeb59c8b0dd2f3765afaef204540161e7377ae6
Timestamp: 1581255788 Timestamp [UCT]: 2020-02-09 13:43:08 Age [y:d:h:m:s]: 04:334:08:57:31
Block: 61432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131036 RingCT/type: yes/0
Extra: 015ef008a510af91cf8c775981fdeb59c8b0dd2f3765afaef204540161e7377ae60211000000108a2ee0d9000000000000000000

1 output(s) for total of 384.106006545000 dcy

stealth address amount amount idx
00: 2b4627769c5c9ed4388248b1118e5d25c1a1f18592fcd399b171aeff219832a8 384.106006545000 113214 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": 61442, "vin": [ { "gen": { "height": 61432 } } ], "vout": [ { "amount": 384106006545, "target": { "key": "2b4627769c5c9ed4388248b1118e5d25c1a1f18592fcd399b171aeff219832a8" } } ], "extra": [ 1, 94, 240, 8, 165, 16, 175, 145, 207, 140, 119, 89, 129, 253, 235, 89, 200, 176, 221, 47, 55, 101, 175, 174, 242, 4, 84, 1, 97, 231, 55, 122, 230, 2, 17, 0, 0, 0, 16, 138, 46, 224, 217, 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