Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 444e5337985339c192f0f0189a3a25a664da3e6de418ecdd44e67cde2401f237

Tx prefix hash: 63b6eac6cf36c652aed8cc28feab4063246c7ee69c150742df6e6f2bc943c8c5
Tx public key: f0c218cfd4d1fe451617aab94d50498890f4a1ba6f917d0dc179905d96e68b29
Timestamp: 1702587343 Timestamp [UCT]: 2023-12-14 20:55:43 Age [y:d:h:m:s]: 01:123:23:30:34
Block: 913182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349760 RingCT/type: yes/0
Extra: 01f0c218cfd4d1fe451617aab94d50498890f4a1ba6f917d0dc179905d96e68b2902110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 198a7fd0570564f207f95b92709051c901247c732b16ad6b0e6ea206c71eb785 0.600000000000 1370428 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": 913192, "vin": [ { "gen": { "height": 913182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "198a7fd0570564f207f95b92709051c901247c732b16ad6b0e6ea206c71eb785" } } ], "extra": [ 1, 240, 194, 24, 207, 212, 209, 254, 69, 22, 23, 170, 185, 77, 80, 73, 136, 144, 244, 161, 186, 111, 145, 125, 13, 193, 121, 144, 93, 150, 230, 139, 41, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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