Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf27fd428b307c1a4f9beae5b5a797277493a5d37fb507632f5231a70bcb251c

Tx prefix hash: 43f01f2d28490f3ca8612bc499074f4f5c1f50bfc37309d42cb2475a566c33a7
Tx public key: 34dc62257a00d3199ee747395029155a20a5cb45085c5f742be6bbe8409348bd
Timestamp: 1696575905 Timestamp [UCT]: 2023-10-06 07:05:05 Age [y:d:h:m:s]: 01:181:08:54:41
Block: 863555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390680 RingCT/type: yes/0
Extra: 0134dc62257a00d3199ee747395029155a20a5cb45085c5f742be6bbe8409348bd021100000011faf35c9c000000000000000000

1 output(s) for total of 0.844663724000 dcy

stealth address amount amount idx
00: f05fca17e6f728b2ca4a1b04d15e924fc57382a82cb838a34dc83e569d9bfc29 0.844663724000 1318017 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": 863565, "vin": [ { "gen": { "height": 863555 } } ], "vout": [ { "amount": 844663724, "target": { "key": "f05fca17e6f728b2ca4a1b04d15e924fc57382a82cb838a34dc83e569d9bfc29" } } ], "extra": [ 1, 52, 220, 98, 37, 122, 0, 211, 25, 158, 231, 71, 57, 80, 41, 21, 90, 32, 165, 203, 69, 8, 92, 95, 116, 43, 230, 187, 232, 64, 147, 72, 189, 2, 17, 0, 0, 0, 17, 250, 243, 92, 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