Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c79352c2044b9fb1c6328e7e6befe683a6c72956dc7eb5783e10f82b66d00dcf

Tx prefix hash: 13f75b90a189e73809a7be2567cc8070f3633f7ee55d467b2af0a7a8246dc2b9
Tx public key: 826d8b3f6f4b17fbd98bdb683e0218027f80afaade17bd1ef16a7b349e943b33
Timestamp: 1717561530 Timestamp [UCT]: 2024-06-05 04:25:30 Age [y:d:h:m:s]: 01:160:04:04:12
Block: 1037345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373045 RingCT/type: yes/0
Extra: 01826d8b3f6f4b17fbd98bdb683e0218027f80afaade17bd1ef16a7b349e943b3302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ca78a6e8e766f246931106c45929e7122dbae1e5ea9158e90cc830d21840027 0.600000000000 1505876 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": 1037355, "vin": [ { "gen": { "height": 1037345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ca78a6e8e766f246931106c45929e7122dbae1e5ea9158e90cc830d21840027" } } ], "extra": [ 1, 130, 109, 139, 63, 111, 75, 23, 251, 217, 139, 219, 104, 62, 2, 24, 2, 127, 128, 175, 170, 222, 23, 189, 30, 241, 106, 123, 52, 158, 148, 59, 51, 2, 17, 0, 0, 0, 1, 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