Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f473228e295579a23370799e0a95e6ebda6c3ba00a4e7dd3c4967597180c6bf3

Tx prefix hash: 9bd67aeb71abb19337a18c0f86919167138dfca298e0e2dbdb2e6c815fb40908
Tx public key: 121b819e954cce98249166f9dd8e88b5c1adbb3d8b2b65915cde69b195c9dd3a
Timestamp: 1671839486 Timestamp [UCT]: 2022-12-23 23:51:26 Age [y:d:h:m:s]: 02:066:19:00:04
Block: 659159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 569391 RingCT/type: yes/0
Extra: 01121b819e954cce98249166f9dd8e88b5c1adbb3d8b2b65915cde69b195c9dd3a02110000000133af99f4000000000000000000

1 output(s) for total of 4.017284381000 dcy

stealth address amount amount idx
00: 0bfbbf2d1632cd1a5667ca15139a08912b903818177fa2f74faf89a822779a6e 4.017284381000 1099854 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": 659169, "vin": [ { "gen": { "height": 659159 } } ], "vout": [ { "amount": 4017284381, "target": { "key": "0bfbbf2d1632cd1a5667ca15139a08912b903818177fa2f74faf89a822779a6e" } } ], "extra": [ 1, 18, 27, 129, 158, 149, 76, 206, 152, 36, 145, 102, 249, 221, 142, 136, 181, 193, 173, 187, 61, 139, 43, 101, 145, 92, 222, 105, 177, 149, 201, 221, 58, 2, 17, 0, 0, 0, 1, 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