Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14d9c99ed2549f4da995ec9498edafb785002b84b1433b58e09f06a39fe4ad9b

Tx prefix hash: 6487028b7ce2d5f1d6cf00ff5bb373ed8beeb0ed67fca99127a157b25e7ac935
Tx public key: d734fb4178cee179ef48b62afb935f9214d5b0f706d24e160bb843ef52a436c9
Timestamp: 1583640161 Timestamp [UCT]: 2020-03-08 04:02:41 Age [y:d:h:m:s]: 04:294:00:36:17
Block: 78563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104797 RingCT/type: yes/0
Extra: 01d734fb4178cee179ef48b62afb935f9214d5b0f706d24e160bb843ef52a436c902110000003a6d997e00000000000000000000

1 output(s) for total of 337.045831297000 dcy

stealth address amount amount idx
00: 5b0f000d852277f71614a78aee5fb264136d951c04de7d299c1a648faee48b5b 337.045831297000 144029 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": 78573, "vin": [ { "gen": { "height": 78563 } } ], "vout": [ { "amount": 337045831297, "target": { "key": "5b0f000d852277f71614a78aee5fb264136d951c04de7d299c1a648faee48b5b" } } ], "extra": [ 1, 215, 52, 251, 65, 120, 206, 225, 121, 239, 72, 182, 42, 251, 147, 95, 146, 20, 213, 176, 247, 6, 210, 78, 22, 11, 184, 67, 239, 82, 164, 54, 201, 2, 17, 0, 0, 0, 58, 109, 153, 126, 0, 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