Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e1fd74e1b834ed74a90561ffbef6bffc9fd6187494ef1f3c31304c575495683

Tx prefix hash: 6b3de729b9d79cf11f59fac0401d5caf1c410e2d6377f58cdc4bd99f2ec677d2
Tx public key: 16ea7c39ca07556f511904561c97514106a560d4213273c7ec05445631822f22
Timestamp: 1697288482 Timestamp [UCT]: 2023-10-14 13:01:22 Age [y:d:h:m:s]: 02:028:11:42:28
Block: 869468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 539978 RingCT/type: yes/0
Extra: 0116ea7c39ca07556f511904561c97514106a560d4213273c7ec05445631822f2202110000000275e3f0e9000000000000000000

1 output(s) for total of 0.807405328000 dcy

stealth address amount amount idx
00: 40bc498c0c19e93ab580f3c3df42f75b12be4944b3d9e2b43052067c94dff774 0.807405328000 1324315 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": 869478, "vin": [ { "gen": { "height": 869468 } } ], "vout": [ { "amount": 807405328, "target": { "key": "40bc498c0c19e93ab580f3c3df42f75b12be4944b3d9e2b43052067c94dff774" } } ], "extra": [ 1, 22, 234, 124, 57, 202, 7, 85, 111, 81, 25, 4, 86, 28, 151, 81, 65, 6, 165, 96, 212, 33, 50, 115, 199, 236, 5, 68, 86, 49, 130, 47, 34, 2, 17, 0, 0, 0, 2, 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