Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4135ee4a4994f1e6fce83854e1513bea2b24ed9edc65c6683d51f99d26ea4307

Tx prefix hash: 1f8b1fb6480dfc43826e34fd96af841a74c2238adbb17e8031df48daa317bbb6
Tx public key: 0c9db34ab2eb4a20dbe3c2ea3e75d62de6ec568ae9d623dc8d82e94a63b21e2d
Timestamp: 1710289117 Timestamp [UCT]: 2024-03-13 00:18:37 Age [y:d:h:m:s]: 01:061:06:13:39
Block: 977054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304784 RingCT/type: yes/0
Extra: 010c9db34ab2eb4a20dbe3c2ea3e75d62de6ec568ae9d623dc8d82e94a63b21e2d0211000000021c2d361c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b6c16d83b5156a8fb9ed3870a635350aeb58360da973ffe33c9c5dee8544c2a 0.600000000000 1437055 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": 977064, "vin": [ { "gen": { "height": 977054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b6c16d83b5156a8fb9ed3870a635350aeb58360da973ffe33c9c5dee8544c2a" } } ], "extra": [ 1, 12, 157, 179, 74, 178, 235, 74, 32, 219, 227, 194, 234, 62, 117, 214, 45, 230, 236, 86, 138, 233, 214, 35, 220, 141, 130, 233, 74, 99, 178, 30, 45, 2, 17, 0, 0, 0, 2, 28, 45, 54, 28, 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