Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4b76eebed5dc162142fbc6453ac02b51d74aed0b3b11c94c1c46adc8455c6ab

Tx prefix hash: 58eb96028689220fa23c67d3bc96c671c7a2f4500c281d2320e77f3a76e37d10
Tx public key: db5630d3fdddc4c6054063ae5062b80148a20bc53ea06e1757ea74f22d4640c4
Timestamp: 1684841644 Timestamp [UCT]: 2023-05-23 11:34:04 Age [y:d:h:m:s]: 01:335:11:54:17
Block: 766338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500981 RingCT/type: yes/0
Extra: 01db5630d3fdddc4c6054063ae5062b80148a20bc53ea06e1757ea74f22d4640c402110000000575e3f0e9000000000000000000

1 output(s) for total of 1.773390033000 dcy

stealth address amount amount idx
00: 09d1752d40cdfbb9345de8094503f89968b22a232f036fe052399184048f56bf 1.773390033000 1215365 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": 766348, "vin": [ { "gen": { "height": 766338 } } ], "vout": [ { "amount": 1773390033, "target": { "key": "09d1752d40cdfbb9345de8094503f89968b22a232f036fe052399184048f56bf" } } ], "extra": [ 1, 219, 86, 48, 211, 253, 221, 196, 198, 5, 64, 99, 174, 80, 98, 184, 1, 72, 162, 11, 197, 62, 160, 110, 23, 87, 234, 116, 242, 45, 70, 64, 196, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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