Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd8d6190011330150b678d6dbf246a45e54f0db94e50dada5bf1ab1ce2496913

Tx prefix hash: 65c347b00261fa7f885243a181fb78ca0f9b471b0d386cc830e7ff091f69fac0
Tx public key: 2d053448f0471aac3b811706acdcacdb7f4e706a025ff492598d8c91c5c08b1b
Timestamp: 1723630705 Timestamp [UCT]: 2024-08-14 10:18:25 Age [y:d:h:m:s]: 01:098:04:11:44
Block: 1087661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328627 RingCT/type: yes/0
Extra: 012d053448f0471aac3b811706acdcacdb7f4e706a025ff492598d8c91c5c08b1b02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd0ae3a1744bf4f61a00740d82408dc28a2406267b04ebfe1168ac89ce9cb97e 0.600000000000 1562272 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": 1087671, "vin": [ { "gen": { "height": 1087661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd0ae3a1744bf4f61a00740d82408dc28a2406267b04ebfe1168ac89ce9cb97e" } } ], "extra": [ 1, 45, 5, 52, 72, 240, 71, 26, 172, 59, 129, 23, 6, 172, 220, 172, 219, 127, 78, 112, 106, 2, 95, 244, 146, 89, 141, 140, 145, 197, 192, 139, 27, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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