Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb0d9fb7c580ff7e29f842c67b20570df6d06f8a21b0193f8b12d4f6e5114b3f

Tx prefix hash: 643adee45bd7ff9b5c21fb906b9e199725cbfbcef2392ae1d142509071f5d0ec
Tx public key: dca995355bc9c7b07325c86112ca9d8ba7d908459c0b6ff334b0b500679e8724
Timestamp: 1709249552 Timestamp [UCT]: 2024-02-29 23:32:32 Age [y:d:h:m:s]: 00:341:23:13:10
Block: 968436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244503 RingCT/type: yes/0
Extra: 01dca995355bc9c7b07325c86112ca9d8ba7d908459c0b6ff334b0b500679e872402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 593ccc77bd74b943469bde6ef4cf09a22f48e6f82ec891253e1cf9921a217850 0.600000000000 1428251 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": 968446, "vin": [ { "gen": { "height": 968436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "593ccc77bd74b943469bde6ef4cf09a22f48e6f82ec891253e1cf9921a217850" } } ], "extra": [ 1, 220, 169, 149, 53, 91, 201, 199, 176, 115, 37, 200, 97, 18, 202, 157, 139, 167, 217, 8, 69, 156, 11, 111, 243, 52, 176, 181, 0, 103, 158, 135, 36, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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