Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98db3d9ab9b549cbf0bc078e778a31cea96af45bd9e701a66e96481315d0c69a

Tx prefix hash: 75fe11d7749eeb9a2e22e8ff95ebc3e3f067d1965ca9e5d96f8b0aa1fe54bb1a
Tx public key: e8712fda5109dc0a680981f049f4fa1c60b3e151efe503b0a936b6351339e473
Timestamp: 1695470418 Timestamp [UCT]: 2023-09-23 12:00:18 Age [y:d:h:m:s]: 01:195:03:39:41
Block: 854386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400543 RingCT/type: yes/0
Extra: 01e8712fda5109dc0a680981f049f4fa1c60b3e151efe503b0a936b6351339e4730211000000034b8f5122000000000000000000

1 output(s) for total of 0.905867252000 dcy

stealth address amount amount idx
00: 0552c64316b3d99bd4531fd047677f531cf542d7d685d9a2a058d7e4f8d6d0b0 0.905867252000 1308356 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": 854396, "vin": [ { "gen": { "height": 854386 } } ], "vout": [ { "amount": 905867252, "target": { "key": "0552c64316b3d99bd4531fd047677f531cf542d7d685d9a2a058d7e4f8d6d0b0" } } ], "extra": [ 1, 232, 113, 47, 218, 81, 9, 220, 10, 104, 9, 129, 240, 73, 244, 250, 28, 96, 179, 225, 81, 239, 229, 3, 176, 169, 54, 182, 53, 19, 57, 228, 115, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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