Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caeefd614cb87cf6d4a4e656cf1ef942a1058685e09cbbbe5db14cb22da5cfc0

Tx prefix hash: 199e01f3f17d4ed5f4f50a7eb24e421760027a41342f3837f10ef63b53a76b41
Tx public key: 8dd9547554b1e6a98bd84cd57e0a5eac3361393087ca52fef64fc79bf3b72d9c
Timestamp: 1675253197 Timestamp [UCT]: 2023-02-01 12:06:37 Age [y:d:h:m:s]: 02:024:19:36:15
Block: 687462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 539320 RingCT/type: yes/0
Extra: 018dd9547554b1e6a98bd84cd57e0a5eac3361393087ca52fef64fc79bf3b72d9c02110000000b5029cbac000000000000000000

1 output(s) for total of 3.237076378000 dcy

stealth address amount amount idx
00: 4f9426a328f27a6095784939450ad1e23e1bb6c33aa878505a88c8b372cfdfd8 3.237076378000 1130029 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": 687472, "vin": [ { "gen": { "height": 687462 } } ], "vout": [ { "amount": 3237076378, "target": { "key": "4f9426a328f27a6095784939450ad1e23e1bb6c33aa878505a88c8b372cfdfd8" } } ], "extra": [ 1, 141, 217, 84, 117, 84, 177, 230, 169, 139, 216, 76, 213, 126, 10, 94, 172, 51, 97, 57, 48, 135, 202, 82, 254, 246, 79, 199, 155, 243, 183, 45, 156, 2, 17, 0, 0, 0, 11, 80, 41, 203, 172, 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