Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7494828ab5109e46a5c428815fbee1a8ac16f1f1a38be91a646464c7c67b9f9f

Tx prefix hash: 9adc3ee348dd9770c73ce75f8348cef33651346e4facde8954fc602bb51191bf
Tx public key: b61a0ed6f4d0941d47cf8b423818a5d2cce04ce60bc20a8c65f2a6add64386f6
Timestamp: 1712106507 Timestamp [UCT]: 2024-04-03 01:08:27 Age [y:d:h:m:s]: 01:221:16:14:05
Block: 992084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417138 RingCT/type: yes/0
Extra: 01b61a0ed6f4d0941d47cf8b423818a5d2cce04ce60bc20a8c65f2a6add64386f60211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc5cfde40927b4bc4a217a229b1204960469b892bc6cdbe142284624e1636956 0.600000000000 1452420 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": 992094, "vin": [ { "gen": { "height": 992084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc5cfde40927b4bc4a217a229b1204960469b892bc6cdbe142284624e1636956" } } ], "extra": [ 1, 182, 26, 14, 214, 244, 208, 148, 29, 71, 207, 139, 66, 56, 24, 165, 210, 204, 224, 76, 230, 11, 194, 10, 140, 101, 242, 166, 173, 214, 67, 134, 246, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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