Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4da759ac8cb4bf40be1d683c12f91f0baa2f579a0716832c024cdb2a9dc92f49

Tx prefix hash: bd0eae830eed6f911d6c25d730435d48e4fc721a0adee456322aef33dce89fb7
Tx public key: dc75475c99887c0c77f66d09f1c987eb4c9252cb935635ca514ffc26809899aa
Timestamp: 1700802827 Timestamp [UCT]: 2023-11-24 05:13:47 Age [y:d:h:m:s]: 01:132:16:29:42
Block: 898395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355997 RingCT/type: yes/0
Extra: 01dc75475c99887c0c77f66d09f1c987eb4c9252cb935635ca514ffc26809899aa02110000000433af99f4000000000000000000

1 output(s) for total of 0.647506913000 dcy

stealth address amount amount idx
00: 9915a3c67f7a39fafd01d80e2e48ce1532a4c072a0453f58df3a2be2f9d3f8f8 0.647506913000 1354808 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": 898405, "vin": [ { "gen": { "height": 898395 } } ], "vout": [ { "amount": 647506913, "target": { "key": "9915a3c67f7a39fafd01d80e2e48ce1532a4c072a0453f58df3a2be2f9d3f8f8" } } ], "extra": [ 1, 220, 117, 71, 92, 153, 136, 124, 12, 119, 246, 109, 9, 241, 201, 135, 235, 76, 146, 82, 203, 147, 86, 53, 202, 81, 79, 252, 38, 128, 152, 153, 170, 2, 17, 0, 0, 0, 4, 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