Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26160029b1ac5cd7065ca0a2cb674b367a9799eacfb1931d1a71e694f655d106

Tx prefix hash: 7c7ff1813178f20e7527b15a80000dc628d923b761919fb79d35fed2c1b4f0de
Tx public key: 2bd3c3c283a1b3aceba5ebfea64608c42f19b8cb7e90043287e96587e74143b5
Timestamp: 1735749494 Timestamp [UCT]: 2025-01-01 16:38:14 Age [y:d:h:m:s]: 00:172:05:09:15
Block: 1187991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122716 RingCT/type: yes/0
Extra: 012bd3c3c283a1b3aceba5ebfea64608c42f19b8cb7e90043287e96587e74143b50211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37da3da0d015311933c91e9ac57164882f40b2f449f5da9d868c045967ed91a0 0.600000000000 1674490 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": 1188001, "vin": [ { "gen": { "height": 1187991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37da3da0d015311933c91e9ac57164882f40b2f449f5da9d868c045967ed91a0" } } ], "extra": [ 1, 43, 211, 195, 194, 131, 161, 179, 172, 235, 165, 235, 254, 166, 70, 8, 196, 47, 25, 184, 203, 126, 144, 4, 50, 135, 233, 101, 135, 231, 65, 67, 181, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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