Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c36c99eb107ce79cc355b9748b58f773a7bed30f20a085d26086bfbea5af5cf

Tx prefix hash: bb3fa1c07647bb80caf8ba722fd1260f661db44b7fcb9a6cd19ff5df57384a8d
Tx public key: c7eea03d52a5cc72714634b6e3cd9bd552ab93d1e144d7e171b2b6c9830c2c9d
Timestamp: 1693593084 Timestamp [UCT]: 2023-09-01 18:31:24 Age [y:d:h:m:s]: 02:069:14:42:23
Block: 838814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 569452 RingCT/type: yes/0
Extra: 01c7eea03d52a5cc72714634b6e3cd9bd552ab93d1e144d7e171b2b6c9830c2c9d02110000000d33af99f4000000000000000000

1 output(s) for total of 1.020143068000 dcy

stealth address amount amount idx
00: c70cabf3636d18cd17ee33bf737f71b567eb4ee5fedc0c4d39210a6249f507dd 1.020143068000 1291600 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": 838824, "vin": [ { "gen": { "height": 838814 } } ], "vout": [ { "amount": 1020143068, "target": { "key": "c70cabf3636d18cd17ee33bf737f71b567eb4ee5fedc0c4d39210a6249f507dd" } } ], "extra": [ 1, 199, 238, 160, 61, 82, 165, 204, 114, 113, 70, 52, 182, 227, 205, 155, 213, 82, 171, 147, 209, 225, 68, 215, 225, 113, 178, 182, 201, 131, 12, 44, 157, 2, 17, 0, 0, 0, 13, 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