Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c63463b095d9ef3c096b24e99fc8eeb74f7fa941c55bd983412cba9e6e913916

Tx prefix hash: 28f9fc3b4e94877d1b83815fd7264d782b3368d7e92620eca9bc358d0b4d7605
Tx public key: a035ffc7898deef0180a8f899c4011c3fd2344391f3a75834f822ac75bf04ba5
Timestamp: 1694067235 Timestamp [UCT]: 2023-09-07 06:13:55 Age [y:d:h:m:s]: 01:170:06:11:02
Block: 842749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382746 RingCT/type: yes/0
Extra: 01a035ffc7898deef0180a8f899c4011c3fd2344391f3a75834f822ac75bf04ba502110000002f4b8f5122000000000000000000

1 output(s) for total of 0.990011720000 dcy

stealth address amount amount idx
00: 1be6e915df9d15dabd70e848d57b61e68e91ba7f567eca175ab37b67a6c86eb9 0.990011720000 1295899 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": 842759, "vin": [ { "gen": { "height": 842749 } } ], "vout": [ { "amount": 990011720, "target": { "key": "1be6e915df9d15dabd70e848d57b61e68e91ba7f567eca175ab37b67a6c86eb9" } } ], "extra": [ 1, 160, 53, 255, 199, 137, 141, 238, 240, 24, 10, 143, 137, 156, 64, 17, 195, 253, 35, 68, 57, 31, 58, 117, 131, 79, 130, 42, 199, 91, 240, 75, 165, 2, 17, 0, 0, 0, 47, 75, 143, 81, 34, 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