Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bc05cb4be379ca3bdf3a3dcde3e6f148a468f39654d281381591930213ff5e2

Tx prefix hash: d52e086c9dbacff8dae1a32ccde2cdf4a68878783fb98cbe137de9ac80cce981
Tx public key: 050854bbbb926f24412ee3a4cb6d95ebb50e25683aa6d0a498a5b9d552b1cc0c
Timestamp: 1710186381 Timestamp [UCT]: 2024-03-11 19:46:21 Age [y:d:h:m:s]: 00:350:11:32:04
Block: 976208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250564 RingCT/type: yes/0
Extra: 01050854bbbb926f24412ee3a4cb6d95ebb50e25683aa6d0a498a5b9d552b1cc0c0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e01b653f5906629676320e5fcac0f2ca4f83a8f5f827c65471246a282bc56bb0 0.600000000000 1436199 of 15

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": 976218, "vin": [ { "gen": { "height": 976208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e01b653f5906629676320e5fcac0f2ca4f83a8f5f827c65471246a282bc56bb0" } } ], "extra": [ 1, 5, 8, 84, 187, 187, 146, 111, 36, 65, 46, 227, 164, 203, 109, 149, 235, 181, 14, 37, 104, 58, 166, 208, 164, 152, 165, 185, 213, 82, 177, 204, 12, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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