Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cf47c28c28ed9895e10b7245fcd5cd2cc521a3adf988a62d3041493c188961d

Tx prefix hash: 8c258f2104eb884bd87bedbfae6db2c81eb4b4d70e880b974ca1edaca5c9d23d
Tx public key: 6de44a6780d03135e3e416c3fbcd6903458b7ace349a8971e8ba0bdf64c9a6c6
Timestamp: 1583240990 Timestamp [UCT]: 2020-03-03 13:09:50 Age [y:d:h:m:s]: 04:299:19:22:18
Block: 75860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108313 RingCT/type: yes/0
Extra: 016de44a6780d03135e3e416c3fbcd6903458b7ace349a8971e8ba0bdf64c9a6c60211000000052895ae00000000000000000000

1 output(s) for total of 344.068667097000 dcy

stealth address amount amount idx
00: 96496ef44b777ec3b9bcba45cef303a29e27fe698c4436f1ae2ff286476fa468 344.068667097000 139849 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": 75870, "vin": [ { "gen": { "height": 75860 } } ], "vout": [ { "amount": 344068667097, "target": { "key": "96496ef44b777ec3b9bcba45cef303a29e27fe698c4436f1ae2ff286476fa468" } } ], "extra": [ 1, 109, 228, 74, 103, 128, 208, 49, 53, 227, 228, 22, 195, 251, 205, 105, 3, 69, 139, 122, 206, 52, 154, 137, 113, 232, 186, 11, 223, 100, 201, 166, 198, 2, 17, 0, 0, 0, 5, 40, 149, 174, 0, 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