Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fdfccb89420bb966cbd2084f2b2c90d39e548eb0a1f667e65111196a164d851

Tx prefix hash: 2af4e3c5cb16812a82145521248080a0f259a6b9600716bc0d89cb1c751ffe4c
Tx public key: b435f9027a48d9c1535dcaefa65fa60c1386a22e1e5c78ebe6b6fa867a0441c5
Timestamp: 1723215397 Timestamp [UCT]: 2024-08-09 14:56:37 Age [y:d:h:m:s]: 00:259:08:37:30
Block: 1084207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185250 RingCT/type: yes/0
Extra: 01b435f9027a48d9c1535dcaefa65fa60c1386a22e1e5c78ebe6b6fa867a0441c502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38639b56841c1c2a7cf01438a1289054b4c73d998b9a65360f6d20e1cdd308e6 0.600000000000 1558400 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": 1084217, "vin": [ { "gen": { "height": 1084207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38639b56841c1c2a7cf01438a1289054b4c73d998b9a65360f6d20e1cdd308e6" } } ], "extra": [ 1, 180, 53, 249, 2, 122, 72, 217, 193, 83, 93, 202, 239, 166, 95, 166, 12, 19, 134, 162, 46, 30, 92, 120, 235, 230, 182, 250, 134, 122, 4, 65, 197, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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