Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1ff6924daf6b76e0017c07fb7f36aed51f3cf45ff5c65ece6811ba4083ea8ce

Tx prefix hash: 7cc62aa971fda276c075dd16b51ffd711bf0f5dcc3019b325c46852e972ac800
Tx public key: 9c37707943f8230802a1f5809ac0f99c00b496c9ad15c65e2d18c8ae9d45001d
Timestamp: 1732514772 Timestamp [UCT]: 2024-11-25 06:06:12 Age [y:d:h:m:s]: 00:133:07:16:44
Block: 1161204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95083 RingCT/type: yes/0
Extra: 019c37707943f8230802a1f5809ac0f99c00b496c9ad15c65e2d18c8ae9d45001d0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05dbd0690f50243778cce9bc9ba618481d438169b6d93781114293e9e576f76e 0.600000000000 1646855 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": 1161214, "vin": [ { "gen": { "height": 1161204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05dbd0690f50243778cce9bc9ba618481d438169b6d93781114293e9e576f76e" } } ], "extra": [ 1, 156, 55, 112, 121, 67, 248, 35, 8, 2, 161, 245, 128, 154, 192, 249, 156, 0, 180, 150, 201, 173, 21, 198, 94, 45, 24, 200, 174, 157, 69, 0, 29, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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