Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9db38acc64a44e7b25d983ae5dceb682a359846a4b71a7bb22ba73dc23ede126

Tx prefix hash: 06133372178ea8c44e15b43d1df85213fda8e85c42836e349a32d40c92bb8f2d
Tx public key: f9efcfa471f0c9dea63e66d8598c27a2fe66fe345868a49fa0ee88cdbda8a030
Timestamp: 1729074785 Timestamp [UCT]: 2024-10-16 10:33:05 Age [y:d:h:m:s]: 01:028:09:39:46
Block: 1132806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278649 RingCT/type: yes/0
Extra: 01f9efcfa471f0c9dea63e66d8598c27a2fe66fe345868a49fa0ee88cdbda8a0300211000000073cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c92ab372321da33b5b748e9da2124114778b3fb4baa6c0cab7e72c1ef75e7aa 0.600000000000 1615809 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": 1132816, "vin": [ { "gen": { "height": 1132806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c92ab372321da33b5b748e9da2124114778b3fb4baa6c0cab7e72c1ef75e7aa" } } ], "extra": [ 1, 249, 239, 207, 164, 113, 240, 201, 222, 166, 62, 102, 216, 89, 140, 39, 162, 254, 102, 254, 52, 88, 104, 164, 159, 160, 238, 136, 205, 189, 168, 160, 48, 2, 17, 0, 0, 0, 7, 60, 208, 252, 6, 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