Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bb77e3af29dbf6842f4cd3e70647a05ac4ae268776fcd283cee4d04078b9b7e

Tx prefix hash: 1567131346be8e8d128ff31d2b7087134c98aaea514506bceacdd022934bc95c
Tx public key: 9e5de15493f2950b7ba033f6f19b235df68c9f18fbf390d59e7109153f740f84
Timestamp: 1710618922 Timestamp [UCT]: 2024-03-16 19:55:22 Age [y:d:h:m:s]: 00:295:12:52:21
Block: 979800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211553 RingCT/type: yes/0
Extra: 019e5de15493f2950b7ba033f6f19b235df68c9f18fbf390d59e7109153f740f8402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e70beb42bf3eab5ccae0f1db6d1e5c3bf2f5e78e00b2206afc79d60fe8243c0b 0.600000000000 1439855 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": 979810, "vin": [ { "gen": { "height": 979800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e70beb42bf3eab5ccae0f1db6d1e5c3bf2f5e78e00b2206afc79d60fe8243c0b" } } ], "extra": [ 1, 158, 93, 225, 84, 147, 242, 149, 11, 123, 160, 51, 246, 241, 155, 35, 93, 246, 140, 159, 24, 251, 243, 144, 213, 158, 113, 9, 21, 63, 116, 15, 132, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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