Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 102e34f4cf4b47615078b2b1ac1d33266b6f51a93f8292d933f5c4036cbf7f10

Tx prefix hash: 757cd8a87f1e8dca46ca79f9d134d04c9be2f8e381f919c60a958065f8eeb100
Tx public key: c9ebc60b22ac9d698ad1aaf286bda61b0e41f961847651452c009e764efa8af0
Timestamp: 1733112131 Timestamp [UCT]: 2024-12-02 04:02:11 Age [y:d:h:m:s]: 00:125:07:34:27
Block: 1166163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89363 RingCT/type: yes/0
Extra: 01c9ebc60b22ac9d698ad1aaf286bda61b0e41f961847651452c009e764efa8af0021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 554bd09b1aedd1f9f1aa2756842ae0eabf82b2917ce935d40274534aa9c39c65 0.600000000000 1651840 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": 1166173, "vin": [ { "gen": { "height": 1166163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "554bd09b1aedd1f9f1aa2756842ae0eabf82b2917ce935d40274534aa9c39c65" } } ], "extra": [ 1, 201, 235, 198, 11, 34, 172, 157, 105, 138, 209, 170, 242, 134, 189, 166, 27, 14, 65, 249, 97, 132, 118, 81, 69, 44, 0, 158, 118, 78, 250, 138, 240, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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