Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c899125a99bd410919623a92c1be8f788446bd9241ba50d7c4f7aa7363f1f4fe

Tx prefix hash: e0791af92246ea45e40ce74029f9c0e27e6e9646c0703fa68bc8c4333ed2f3aa
Tx public key: 9d473e4e2a58a4921d73966a5457f79ac044d68ec43a90d4921d0e092cd17548
Timestamp: 1721669660 Timestamp [UCT]: 2024-07-22 17:34:20 Age [y:d:h:m:s]: 00:256:02:08:42
Block: 1071385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182947 RingCT/type: yes/0
Extra: 019d473e4e2a58a4921d73966a5457f79ac044d68ec43a90d4921d0e092cd17548021100000005e914dd15000000000000000000

1 output(s) for total of 0.615590000000 dcy

stealth address amount amount idx
00: 2f88606d2264f49b127975d11a4c7a067781da1790a0ad41df7608533e5bb8d3 0.615590000000 1543594 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": 1071395, "vin": [ { "gen": { "height": 1071385 } } ], "vout": [ { "amount": 615590000, "target": { "key": "2f88606d2264f49b127975d11a4c7a067781da1790a0ad41df7608533e5bb8d3" } } ], "extra": [ 1, 157, 71, 62, 78, 42, 88, 164, 146, 29, 115, 150, 106, 84, 87, 247, 154, 192, 68, 214, 142, 196, 58, 144, 212, 146, 29, 14, 9, 44, 209, 117, 72, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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