Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5c18b466cca61cc9105a68afef98e03cb8c49a99b260436aff05fb4323a8196

Tx prefix hash: c41d92053290d0b66e4d2f8503e3c8f87a912983b6bea011775df6c6c3cd411a
Tx public key: 61fb51c53feb725805c97966e495989be8cbcc4ca00736332c76763b8124bbf5
Timestamp: 1698436745 Timestamp [UCT]: 2023-10-27 19:59:05 Age [y:d:h:m:s]: 01:224:11:11:01
Block: 878997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421470 RingCT/type: yes/0
Extra: 0161fb51c53feb725805c97966e495989be8cbcc4ca00736332c76763b8124bbf5021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.750789282000 dcy

stealth address amount amount idx
00: bbe3a67878de79ee32f8ae8e162f032d02882e80a669e5a1561a49b05f1ab0d4 0.750789282000 1334493 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": 879007, "vin": [ { "gen": { "height": 878997 } } ], "vout": [ { "amount": 750789282, "target": { "key": "bbe3a67878de79ee32f8ae8e162f032d02882e80a669e5a1561a49b05f1ab0d4" } } ], "extra": [ 1, 97, 251, 81, 197, 63, 235, 114, 88, 5, 201, 121, 102, 228, 149, 152, 155, 232, 203, 204, 76, 160, 7, 54, 51, 44, 118, 118, 59, 129, 36, 187, 245, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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