Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd9ced349ba4cc7ac9a084308ac715f5b029c2e542821d7cb2a759e4332cfaf0

Tx prefix hash: f49d61cb5509b04a273c375c25031ed0926a167dbc8898d8dcb5c26dcbd6aca4
Tx public key: 314ee125805df25e17b855c8df06e8b413b101b59d869c7bc19e26694b443f7b
Timestamp: 1707337448 Timestamp [UCT]: 2024-02-07 20:24:08 Age [y:d:h:m:s]: 01:056:05:12:53
Block: 952576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301217 RingCT/type: yes/0
Extra: 01314ee125805df25e17b855c8df06e8b413b101b59d869c7bc19e26694b443f7b02110000000110a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67e2c9032df5242c1ccee4d46de48ff127b4af1f2533dd8be15c7957229996f2 0.600000000000 1411634 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": 952586, "vin": [ { "gen": { "height": 952576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67e2c9032df5242c1ccee4d46de48ff127b4af1f2533dd8be15c7957229996f2" } } ], "extra": [ 1, 49, 78, 225, 37, 128, 93, 242, 94, 23, 184, 85, 200, 223, 6, 232, 180, 19, 177, 1, 181, 157, 134, 156, 123, 193, 158, 38, 105, 75, 68, 63, 123, 2, 17, 0, 0, 0, 1, 16, 161, 116, 143, 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