Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c80f6deb0d53a20a5b542f46e21aa5b424d2a9abca0b7041da1bd3506a8c13f

Tx prefix hash: d4b4c65985b8fe72e1806d36cf84b918e445d30747bf4064869c68568ca4361a
Tx public key: bb2da8c1e5ac2c91f28d8ff23e497dbf6b4c621535a38aa949e6bce1b1ca8351
Timestamp: 1708262798 Timestamp [UCT]: 2024-02-18 13:26:38 Age [y:d:h:m:s]: 01:055:15:31:13
Block: 960253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300809 RingCT/type: yes/0
Extra: 01bb2da8c1e5ac2c91f28d8ff23e497dbf6b4c621535a38aa949e6bce1b1ca83510211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c7a7c28b37634e5d990a2cf6618ca116fd4a75e0a4d81fa3690f3a5fe736bdd 0.600000000000 1419816 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": 960263, "vin": [ { "gen": { "height": 960253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c7a7c28b37634e5d990a2cf6618ca116fd4a75e0a4d81fa3690f3a5fe736bdd" } } ], "extra": [ 1, 187, 45, 168, 193, 229, 172, 44, 145, 242, 141, 143, 242, 62, 73, 125, 191, 107, 76, 98, 21, 53, 163, 138, 169, 73, 230, 188, 225, 177, 202, 131, 81, 2, 17, 0, 0, 0, 3, 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