Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4110aa106b25d0090cdc12bbf3c253d2c8e04667a65c9f31aa8e0e87ddd4c4e

Tx prefix hash: 4d5124543631184d4b69ffc7eb660bf0795c2b53d1195cab27c815bc1cd4b6de
Tx public key: cf9e5892cea05fb4847e78689c9713c68f46b560df2982492011814293a17a12
Timestamp: 1578450878 Timestamp [UCT]: 2020-01-08 02:34:38 Age [y:d:h:m:s]: 04:327:18:22:38
Block: 40926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123588 RingCT/type: yes/0
Extra: 01cf9e5892cea05fb4847e78689c9713c68f46b560df2982492011814293a17a1202110000000a8a2ee0d9000000000000000000

1 output(s) for total of 449.162522958000 dcy

stealth address amount amount idx
00: 1ae5d707b45fb8103511decbdaab163b9263d0d79771228275fde7514c39baed 449.162522958000 72395 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": 40936, "vin": [ { "gen": { "height": 40926 } } ], "vout": [ { "amount": 449162522958, "target": { "key": "1ae5d707b45fb8103511decbdaab163b9263d0d79771228275fde7514c39baed" } } ], "extra": [ 1, 207, 158, 88, 146, 206, 160, 95, 180, 132, 126, 120, 104, 156, 151, 19, 198, 143, 70, 181, 96, 223, 41, 130, 73, 32, 17, 129, 66, 147, 161, 122, 18, 2, 17, 0, 0, 0, 10, 138, 46, 224, 217, 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