Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 105660dae63516bc034213d59e755f7a9df5dde3bf26c645204fe87dcf856b90

Tx prefix hash: cc80b71bbc2d3ab0beedcc2e9dfe6c0ce94128d2a029d8cf3fcdb937ca9af231
Tx public key: 0e56f6b84a921fb9ed1f2116b7e4aa275c4b17e47bf06b0187c3be457f8b108d
Timestamp: 1701576438 Timestamp [UCT]: 2023-12-03 04:07:18 Age [y:d:h:m:s]: 01:127:02:28:47
Block: 904812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351984 RingCT/type: yes/0
Extra: 010e56f6b84a921fb9ed1f2116b7e4aa275c4b17e47bf06b0187c3be457f8b108d02110000000146113aa8000000000000000000

1 output(s) for total of 0.616569752000 dcy

stealth address amount amount idx
00: e125115464fd74ad9f6f77b143b2ed667779d1a26895c7987e0f1b5fd2873a0a 0.616569752000 1361589 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": 904822, "vin": [ { "gen": { "height": 904812 } } ], "vout": [ { "amount": 616569752, "target": { "key": "e125115464fd74ad9f6f77b143b2ed667779d1a26895c7987e0f1b5fd2873a0a" } } ], "extra": [ 1, 14, 86, 246, 184, 74, 146, 31, 185, 237, 31, 33, 22, 183, 228, 170, 39, 92, 75, 23, 228, 123, 240, 107, 1, 135, 195, 190, 69, 127, 139, 16, 141, 2, 17, 0, 0, 0, 1, 70, 17, 58, 168, 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