Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f365282e57f66cfcc3a1b51f2c2dcaa8afef69d893725401eafdcce9d993f1a

Tx prefix hash: fd712f4ac0769332db0dc21ded4f5cbb3cecdd24d754d61e804952dcba4477b3
Tx public key: 6fccbe7a0542794f916e8effc6dd242c8fb802425a70cb474b6a24c3d08c0a31
Timestamp: 1714406431 Timestamp [UCT]: 2024-04-29 16:00:31 Age [y:d:h:m:s]: 01:185:07:16:27
Block: 1011178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391073 RingCT/type: yes/0
Extra: 016fccbe7a0542794f916e8effc6dd242c8fb802425a70cb474b6a24c3d08c0a310211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fd6c0637d2e30ba13e1bf40bbedac787cce0aae57c904a4af5e4fcd8091f456 0.600000000000 1473342 of 15

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": 1011188, "vin": [ { "gen": { "height": 1011178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fd6c0637d2e30ba13e1bf40bbedac787cce0aae57c904a4af5e4fcd8091f456" } } ], "extra": [ 1, 111, 204, 190, 122, 5, 66, 121, 79, 145, 110, 142, 255, 198, 221, 36, 44, 143, 184, 2, 66, 90, 112, 203, 71, 75, 106, 36, 195, 208, 140, 10, 49, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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