Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1931f682f2bf35acc62c7cc51e7ccf794a0c329c44aaa831c9fbe1c8e2663f38

Tx prefix hash: 703d6b5ee86ee0828f9cce4101d98cecd981b450201764fbcac87d49b8784632
Tx public key: be5059ca2f8c62511acc5975ce5717ec2933e5bf5a83a2704937c9ee0d22815a
Timestamp: 1658907482 Timestamp [UCT]: 2022-07-27 07:38:02 Age [y:d:h:m:s]: 02:291:01:20:42
Block: 552676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 729243 RingCT/type: yes/0
Extra: 01be5059ca2f8c62511acc5975ce5717ec2933e5bf5a83a2704937c9ee0d22815a021100000004ec6d1a1a000000000000000000

1 output(s) for total of 9.052220279000 dcy

stealth address amount amount idx
00: a283d3b6d25bfa56ffa71ee02f8aecebc50307a55b7f1db329b71cb6af00a5f3 9.052220279000 984412 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": 552686, "vin": [ { "gen": { "height": 552676 } } ], "vout": [ { "amount": 9052220279, "target": { "key": "a283d3b6d25bfa56ffa71ee02f8aecebc50307a55b7f1db329b71cb6af00a5f3" } } ], "extra": [ 1, 190, 80, 89, 202, 47, 140, 98, 81, 26, 204, 89, 117, 206, 87, 23, 236, 41, 51, 229, 191, 90, 131, 162, 112, 73, 55, 201, 238, 13, 34, 129, 90, 2, 17, 0, 0, 0, 4, 236, 109, 26, 26, 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