Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b464e026219922f86b56a2a692e1e28f0724c649f945d656af263142839d1242

Tx prefix hash: 25e772adb4f3dd2fbc64369436b2b09f1defdf3ac9107e9e0e484d4c7672e049
Tx public key: 5d42ece6370fd9f54e135e792a86b655b6cd65d7e5acfebadee959319f86a366
Timestamp: 1706503945 Timestamp [UCT]: 2024-01-29 04:52:25 Age [y:d:h:m:s]: 01:116:19:42:51
Block: 945643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344621 RingCT/type: yes/0
Extra: 015d42ece6370fd9f54e135e792a86b655b6cd65d7e5acfebadee959319f86a36602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f93c46a62a822fa83aa56cdaa67a3b7efb7b16a0327967dd3a0aea99228b9f8e 0.600000000000 1403959 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": 945653, "vin": [ { "gen": { "height": 945643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f93c46a62a822fa83aa56cdaa67a3b7efb7b16a0327967dd3a0aea99228b9f8e" } } ], "extra": [ 1, 93, 66, 236, 230, 55, 15, 217, 245, 78, 19, 94, 121, 42, 134, 182, 85, 182, 205, 101, 215, 229, 172, 254, 186, 222, 233, 89, 49, 159, 134, 163, 102, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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