Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcdaca573c2bc0ac671940850d14de8ff26c3c6d86a4a159f0d024b1c3b28533

Tx prefix hash: 9de58a01cf4e67840974d945337de1934323fc2bc66552259d850505f73974d1
Tx public key: 1fef40359485674898cf1cfd9e6689a42ad4b51b9d4e395a93eab4faf007c523
Timestamp: 1663682054 Timestamp [UCT]: 2022-09-20 13:54:14 Age [y:d:h:m:s]: 02:100:06:42:29
Block: 591986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 593261 RingCT/type: yes/0
Extra: 011fef40359485674898cf1cfd9e6689a42ad4b51b9d4e395a93eab4faf007c523021100000002e6d27f9c000000000000000000

1 output(s) for total of 6.706635577000 dcy

stealth address amount amount idx
00: d470d681e6c88649eb05c086e53c84dce7251421c6c55211dabe810be7b96df6 6.706635577000 1026600 of 0

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": 591996, "vin": [ { "gen": { "height": 591986 } } ], "vout": [ { "amount": 6706635577, "target": { "key": "d470d681e6c88649eb05c086e53c84dce7251421c6c55211dabe810be7b96df6" } } ], "extra": [ 1, 31, 239, 64, 53, 148, 133, 103, 72, 152, 207, 28, 253, 158, 102, 137, 164, 42, 212, 181, 27, 157, 78, 57, 90, 147, 234, 180, 250, 240, 7, 197, 35, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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