Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 055c9222c16e1440cfeeb29c329a65044f423731a193cc2005b000a282dcd05b

Tx prefix hash: 766f4b003e711f8c321b519febdefc137ae40963bc99e1528e01cb6f73e046d3
Tx public key: fb3a6ba846e6feab0e77c2f414ffd826d9614f9ee6472d9f93a6b25f2a198c52
Timestamp: 1694519954 Timestamp [UCT]: 2023-09-12 11:59:14 Age [y:d:h:m:s]: 01:242:13:59:26
Block: 846497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434497 RingCT/type: yes/0
Extra: 01fb3a6ba846e6feab0e77c2f414ffd826d9614f9ee6472d9f93a6b25f2a198c52021100000002faf35c9c000000000000000000

1 output(s) for total of 0.962064309000 dcy

stealth address amount amount idx
00: ebc86855e5d0434576f1b68500745c65d340b8242bcecb243454313741f0997c 0.962064309000 1299963 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": 846507, "vin": [ { "gen": { "height": 846497 } } ], "vout": [ { "amount": 962064309, "target": { "key": "ebc86855e5d0434576f1b68500745c65d340b8242bcecb243454313741f0997c" } } ], "extra": [ 1, 251, 58, 107, 168, 70, 230, 254, 171, 14, 119, 194, 244, 20, 255, 216, 38, 217, 97, 79, 158, 230, 71, 45, 159, 147, 166, 178, 95, 42, 25, 140, 82, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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