Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8b27f2faed99196e3376c144e487a052f579faaf841b61b4fc64f82a5b64721

Tx prefix hash: 77547e39edb979d5f74543416233d96e0590926aec2886424a3c82403e7e7ed4
Tx public key: 27cc1f12a92cc32822f1ec1286b0f8b2f4800a7a8b635164599b059aa285f1e4
Timestamp: 1711869583 Timestamp [UCT]: 2024-03-31 07:19:43 Age [y:d:h:m:s]: 01:044:15:20:52
Block: 990170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292879 RingCT/type: yes/0
Extra: 0127cc1f12a92cc32822f1ec1286b0f8b2f4800a7a8b635164599b059aa285f1e402110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 583450ca83d4741ade90a072b04329a2ee7cea98bf9db8525a3d8206f0d96743 0.600000000000 1450492 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": 990180, "vin": [ { "gen": { "height": 990170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "583450ca83d4741ade90a072b04329a2ee7cea98bf9db8525a3d8206f0d96743" } } ], "extra": [ 1, 39, 204, 31, 18, 169, 44, 195, 40, 34, 241, 236, 18, 134, 176, 248, 178, 244, 128, 10, 122, 139, 99, 81, 100, 89, 155, 5, 154, 162, 133, 241, 228, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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